Skip to content

Add examples and use-cases to the JS overview #4933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: kotlin-js-doc-update
Choose a base branch
from

Conversation

JSMonk
Copy link
Member

@JSMonk JSMonk commented Jun 27, 2025

No description provided.

@JSMonk JSMonk requested a review from a team as a code owner June 27, 2025 15:44
@AlejandraPedroza AlejandraPedroza self-assigned this Jul 1, 2025
@AlejandraPedroza AlejandraPedroza changed the base branch from master to kotlin-js-doc-update July 10, 2025 14:40
@AlejandraPedroza AlejandraPedroza force-pushed the bring-back-more-information-to-js-overview branch from 6a3dc35 to f92471f Compare July 10, 2025 14:41
To use third-party libraries from your Kotlin code, you can create your own typesafe wrappers or use community-maintained wrappers.
Additionally, you can use the Kotlin/JS [dynamic type](dynamic-type.md), which lets you skip strict typing and library wrappers, at the cost of type safety.

Kotlin/JS is also compatible with the most common module systems: [ESM](https://tc39.es/ecma262/#sec-modules), [CommonJS](https://nodejs.org/api/modules.html#modules-commonjs-modules),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added links to each module system in the list. Can you please check they are correct?

| [Fullstack Conference CMS](https://github.com/Kotlin/kmp-fullstack-conference-cms/#readme) | Showcases multiple code-sharing approaches, ranging from the simplest to all-in code sharing between [Ktor](https://ktor.io/), [Jetpack Compose](https://developer.android.com/compose), and [Vue.js](https://vuejs.org/) applications. |
| [Todo App on a Compose-HTML-based Kobweb framework](https://github.com/varabyte/kobweb-templates/tree/main/examples/todo/#readme) | Shows how to create a to-do list application by reusing an approach familiar to Android developers. It builds a client UI application powered by the [Kobweb framework](https://kobweb.varabyte.com/). |
| [Simple logic sharing between Android, iOS, and web](https://github.com/Kotlin/kmp-logic-sharing-simple-example/#readme) | Contains a template for building a project with common logic in Kotlin, which is consumed in platform-native UI applications on Android ([Jetpack Compose](https://developer.android.com/compose)), iOS ([SwiftUI](https://developer.apple.com/tutorials/swiftui/)), and web ([React](https://react.dev/)). |
| [Full-stack collaborative to-do list](https://github.com/kotlin-hands-on/jvm-js-fullstack/#readme) | Shows how to create a to-do list application for collaborative work using Kotlin Multiplatform with JS and JVM targets, [Ktor](https://ktor.io/) for the backend, and Kotlin/JS with React for the frontend. |

## Kotlin/JS frameworks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend moving this whole section to a single page inside Kotlin/JS, and in the Overview we can keep the ## Kotlin/JS frameworks heading with the intro and a visible link sending to the page with the list of frameworks. In this way, we keep the Overview conciser with basic information, and we have more chances to expand the frameworks list whenever we need it. What do you think?

Copy link
Contributor

@AlejandraPedroza AlejandraPedroza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this content! I've reviewed it and made some adjustments in style and format. Can you please check the new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants